Maintain owning application information of data for a data storage system

ABSTRACT

A data storage system writes data supplied from a host to data storage in accordance with write I/O of an owning application. A workload manager directs the processing of the supplied data in accordance with the write I/O of the owning application, provides service workload identification describing the write I/O, a storage subsystem control adds the service workload identification to record set information for the data, and a journal management system stores the record set information in a journal. The journaled information, for example, may be employed for performing forensic analysis of data corruption events or to perform security audits, etc.

CROSS REFERENCE TO RELATED APPLICATION

Commonly assigned U.S. application Ser. No. 11/734,097 filed on evendate herewith relates to methods and computer program productsconfigured to maintain owning application information of data for a datastorage system.

DOCUMENT INCORPORATED BY REFERENCE

Commonly assigned U.S. Pat. No. 5,734,818 is incorporated for itsshowing of a data storage system configured to provide self describingrecord sets having prefix headers including time stamps of write I/Ooperations for data storage, for example, for time based sequenceordering of record updates of the data between primary and secondarydata storage sites.

FIELD OF THE INVENTION

This invention relates to data storage system and more particularly todata storage systems configured to write data supplied from a host todata storage in accordance with write I/O of an owning application.

BACKGROUND OF THE INVENTION

Data storage systems provide storage of data from a host that issufficiently reliable that the data may be deleted from the host. Thereliability of the data storage is typically enhanced throughreplication of the data at primary storage and secondary storage. Forexample, the IBM® DS8000 supports an asynchronous data replicationfunction such as that discussed in the incorporated '818 patent, whichincludes the data transfer required to provide the data for both theprimary and secondary data storage. The data transfer may be journaledto effectively recreate data with I/O consistency from a known point intime of the data forward. The journals may be backed up to provide theability to restore some or all data to any point in time covered by thebackup versions.

It may be desirable for the customer to perform forensic analysis ofdata corruption events or perform security audits on which applicationupdated what data when.

SUMMARY OF THE INVENTION

Data storage systems provide journaled information, for example, thatmay be employed for performing forensic analysis of data corruptionevents or to perform security audits, etc. The data storage systems maycomprise one or more data storage control systems and devices, arrangedas primary and/or secondary data storage.

In one embodiment, a data storage system is configured to write datasupplied from a host to data storage in accordance with write I/O of anowning application, and comprises a workload manager configured todirect the processing of the supplied data in accordance with the writeI/O of an owning application, configured to provide service workloadidentification for describing the write I/O, comprises at least onestorage subsystem configured to add the service workload identificationto record set information for the data, and comprises a journalmanagement system configured to store information from the record setinformation in a journal, including the service workload identification.

In another embodiment, the storage subsystem is configured to add theservice workload identification into a Read Record Set prefix, and thejournal management system is configured to provide the information fromthe Read Record Set prefix to the journal.

In a further embodiment, the workload manager is configured to providethe service workload identification for a defined extent CCW whichprovides the service workload identification for the Read Record Setprefix.

In another embodiment, the workload manager is configured to provide theservice workload identification for a prefix CCW which provides theservice workload identification for the Read Record Set prefix.

In another embodiment, the service workload identification comprises aclass of service defined for the owning application by the host.

In a further embodiment, the class of service comprises I/O priorityinformation, and wherein the workload manager is configured to selectthe I/O priority information of the class of service.

For a fuller understanding of the present invention, reference should bemade to the following detailed description taken in conjunction with theaccompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing a data storage system and host system,which may implement the present invention;

FIG. 2 is a data format diagram showing a prefix header of a read recordset, having service workload identification in accordance with thepresent invention;

FIG. 3 is a data format diagram describing fields of a read record set,having service workload identification in accordance with the presentinvention;

FIG. 4 is a block diagram showing an alternative embodiment of a datastorage system and host systems for implementing the present invention;and

FIG. 5 is a flow chart depicting the functions implementing the presentinvention.

DETAILED DESCRIPTION OF THE INVENTION

This invention is described in preferred embodiments in the followingdescription with reference to the Figures, in which like numbersrepresent the same or similar elements. While this invention isdescribed in terms of the best mode for achieving this invention'sobjectives, it will be appreciated by those skilled in the art thatvariations may be accomplished in view of these teachings withoutdeviating from the spirit or scope of the invention.

Referring to FIG. 1, a data storage system 10 is illustrated inconjunction with a host system 12. Typically, the host system 12, whichmay comprise one or more host processors, and may comprise a network,comprises applications 30 that generate data to be stored by the datastorage system 10. The data storage system comprises, for example, astorage control system 15 having at least one subsystem control 18 and anumber of drive devices 16, such as disk drives, for example, in theform of a RAID (Redundant Array of Independent Disks) for JBOD (Just aBranch of Disks). The storage control system 15 may also be incommunication with long term storage such as magnetic tape or opticaldisks 17, for example, in the form of an automated data storage library.An example of a storage control system 15 that may be operated inaccordance with the present invention comprises the IBM® DS 8000.

The storage system 10 incorporates a workload manager (WLM) 20, 20Aconfigured to direct the processing of supplied data for storage. Theworkload manager 20, 20A may reside in the storage control system 15 orin a host system 12, or both. The storage system 10 comprises cache 21for intermediate storage of data and of information employed in theoperation of the storage system. The cache may also comprise diskstorage, or may comprise a portion of the storage subsystem 16. In oneembodiment, the workload manager 20A comprises a component of anoperating system (O/S) 23 of the host system 12 along with an I/Osubsystem (IOS) component 24. In an alternative embodiment, the workloadmanager 20 comprises a component of an operating system 43 of at leastone processor of the storage control system 15 along with an I/Osubsystem component 44.

The workload manager 20 and storage control system subsystem control 18,separately or together, may comprise program code and any suitablelogic, microprocessor, and associated memory and/or data storage forresponding to program code, and the associated memory and/or datastorage may comprise fixed or rewritable memory or data storage devices.The workload manager 20 may comprise program code within the programcode of the storage system 10, or may comprise an application employedby the storage system 10. The program code may be supplied to thestorage system directly as from a data storage device or memory, forexample by an input from an optical disk or floppy disk, for example atan operator panel 22 or drive of the storage system 10, or by being readfrom a magnetic tape cartridge, for example at a drive device 17, orfrom a network, for example via host system 12, or by any other suitablemeans. The workload manager 20 may be physically located at the hostsystem 12, the storage control system 15 or any point in the datastorage system 10, or spread across the data storage system.

The data storage system 10 may comprise primary and secondary sites, forexample, with host system 12, storage control system 15 with drivedevices 16 comprising the primary site, and storage control system 25with subsystem control 28 and drive devices 26 comprising a secondarysite. The data storage system may thus provide data storage at theprimary site and shadow the data at the secondary site, transferring thedata asynchronously, employing a storage data mover 29 to formconsistency groups, as described in the incorporated '818 patent.

In the incorporated '818 patent, applications 30 at the primary sitegenerate record updates, and a secondary site, for example, remote fromthe primary site, shadows the record updates. The data storage system 10comprises a sysplex timer for synchronizing time dependent processes inthe primary site. The primary storage control system 15 responds towrite I/O operations for the record updates, and conducts write I/Ooperations to the primary storage subsystem 16 for each record update,the write I/O operations being synchronized to the sysplex timer. Theprimary storage subsystem 16 accordingly receives the write I/Ooperations and stores the data.

The primary subsystem control 18 sees that a write I/O operation isdirected to a volume also stored at the secondary site, and builds aRead Record Set prefix with the specific storage information in itscache 21. The subsystem control thus collects record set information foreach record update and appends a prefix header to a predetermined groupof record set information. The prefix header and the predetermined groupof record set information form self describing record sets, includingthe data updates.

The record set information includes, inter alia, a record updatesequence number and a record update time. The prefix header includes,inter alia, an operational time stamp, a time interval group number, anda record read time.

The storage data mover 29 reads the RRS's from the subsystem control(s)18 and forms consistency groups which are written to a journal, forexample, stored in cache 21. The consistency groups are all I/Os of asmall period of time. It is important that cross volume and crossstorage control system data consistency is maintained. The record setsare transmitted over communication link 35 to a secondary storagecontrol system 25 which orders the record updates from each consistencygroup for writing to the secondary storage control system 25 in an orderconsistent with a sequence that the record updates were written to theprimary storage control system 15.

In one embodiment of the incorporated '818 patent, the storage datamover 29 creates a journal record for each self describing record,including the prefix header. The journal record may be transmitted tothe secondary storage control system 25 and the information employed toform the consistency groups and to control the writing of the recordupdates to the secondary storage subsystem 26.

Referring to FIGS. 1, 2 and 3, in one embodiment of the presentinvention, the data storage system 10 is configured to write datasupplied from a host 12 to data storage in accordance with write I/O ofan owning application 30. Examples of applications may compriseaccounting, payroll, information management and data base applications,etc. The data storage may comprise a single device, a single site withmultiple storage devices, a single site with multiple storage systems,primary and secondary sites as illustrated in FIG. 1, or primary andmultiple secondary sites.

The present invention comprises data storage systems, methods andcomputer program products for providing journaled information, forexample, that may be employed for performing forensic analysis of datacorruption events or to perform security audits, etc., in which theowning applications of the I/O's are identified.

A workload manager 20 is configured to direct the processing of thesupplied data with respect to the data storage system in accordance withthe write I/O of an owning application 30. The workload manager 20 maybe resident in the storage control system 15, the host 12 (illustratedas 20A), or both, and herein is considered to comprise an element of thedata storage system 10. Herein, references to workload manager 20 alsoor alternatively refer to 20A. The storage control system 15 isconfigured to store data with respect to storage devices 16, and thestorage control system 25 is configured to store data with respect tostorage devices 26. The present invention can take the form of anentirely hardware embodiment, or an embodiment containing both hardwareand software elements. In a preferred embodiment, the invention includesbut is not limited to resident software, firmware, microcode, etc.Furthermore, the invention can take the form of a computer programproduct accessible from a computer usable or computer readable mediumproviding program code for use by or in connection with a computer orany instruction execution system. For the purposes of this description,a computer usable or computer readable medium can be any apparatus thatcan contain or store the program for use by or in connection with theinstruction execution system, apparatus or device.

The medium can be an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system (or apparatus or device) or apropagation medium. Examples of a computer readable medium include asemiconductor or solid state memory, magnetic tape, a removable computerdiskette, a random access memory (RAM), a read only memory (ROM), arigid magnetic disk and an optical disk. Current examples of opticaldisks include compact disk—read only memory (CD-ROM), compactdisk—read/write (CD-R/W) and DVD.

A data processing system suitable for storing and/or executing programcode will include at least one processor coupled directly or indirectlyto memory elements through a system bus. The memory elements can includelocal memory employed during actual execution of the program code, bulkstorage, and cache memories which provide temporary storage of at leastsome program code in order to reduce the number of times code must beretrieved from bulk storage during execution. Network adapters may becoupled to the system to enable the data processing system to becomecoupled to other data processing systems or remote devices throughintervening private or public networks. Modems, cable modems andEthernet cards are just a few of the currently available types ofnetwork adapters.

The customer, via the host 12, defines what applications (workloads) 30to assign to which class of service. A class of service designation mayinclude or comprise an I/O priority. For example, an IBM® zOS computeroperating system allows customers to initially define class of servicefor each application which is assigned to workload by the workloadmanager 20. There are currently some 100 unique classes available oneach managed system. Defined in the class of service is an I/O prioritywhich is given to each I/O operation for that class of service. Theclass of service may reflect the customer defined relative businesspriorities on a workload by workload basis. Herein, class of service orI/O priority, or any similar designation is called “service workloadidentification”.

The workload manager 20 comprises an infrastructure to track and manageworkloads via the class of service that the I/O chain is on behalf of,and as a result it can provide the information in the write chain in amanner similar to its providing I/O priority for the workload. Theresultant unit of work information is preserved through the operatingsystem function/middleware such that when the I/O is executed, the I/Opriority that the customer has previously defined for that workload issent with the I/O.

The workload manager 20 is configured to provide the service workloadidentification describing the write I/O for use by the I/O subsystem 24,44. The workload manager is configured to provide the service workloadidentification for all I/O on behalf of a unit of work that is to bedirected to the data storage system.

The I/O subsystem 24, 44 accesses the service workload identificationfrom the workload manager (along with other information) and providesthe service workload identification to the storage subsystem control 18via a Channel Command Work (CCW) or equivalent. Examples of a CCW arethe define extent CCW or prefix CCW. For example, the define extent CCWcreated is modified to provide some additional information including theservice workload identification, and is added to a write I/O chain.Alternatively, a prefix CCW is generated and includes the serviceworkload identification, and is added to a write I/O chain. Herein, theCCW's are termed “provided” by the workload manager without regard tothe initial source of the CCW.

Referring to FIG. 2, the storage subsystem control 18 recognizes thatthe referenced I/O is directed to a volume that is or is to be stored inboth the primary and secondary sites (termed as “XRC” or extended remotecopy), and builds a Read Record Set prefix 500 with the specific storageinformation in its cache 21 as discussed above. Included in the ReadRecord Set prefix is the service workload identification 100 as providedby the workload manager 20. The remainder of the prefix header 500 isexplained by the incorporated '818 patent and is related to the formatfor each self describing record set. The prefix header may comprise atotal data length 501 for describing the total length of the prefixheader 500 and the full primary record set information for the recordset. An operational time stamp 502 is a time stamp indicating a starttime for the operational set that is currently being processed. A timeinterval group number 503 identifies a time interval (bounded byoperational time stamp 502 and a records read time 507) for which thecurrent record sets belong. A sequence number within group 504 isderived based upon an identification of a write sequence order ofapplication write I/Os for each record set within a given time intervalgroup 503. A primary substorage identification (SSID) 505 uniquelyidentifies the specific storage controller of the primary storagecontrol system 15 for each record set. A secondary target volume 506 isassigned, and a records read time 507 provides an operational time stampthat indicates an end time for the read record set process currentinterval. The operational time stamp 502 and the records read time 507are used to group sets of read record sets from the primary storagecontrol system 15.

Referring to FIG. 3, the record set information 600 is collected by thestorage data mover 29 by reading all of Read Record Sets 500 from thesubsystem control(s) 18 and the data mover forms the consistency groups.The record set information incorporates the service workloadidentification 100 from the Read Record Set prefix header 500.

The remainder of the record set information 600 is explained by theincorporated '818 patent and is related to the format for each selfdescribing record set. Update specific information 601-610 includes aprimary device unit address 601 of each record indicating the actualdata storage device or set of devices (which may be virtual) that therecord update occurred on. A cylinder number/head number (which may bevirtual) indicates a location on the data storage device or set ofdevices. A primary storage controller session identifier (SSID) 603 isthe same as the primary SSID 505. Status flags 604 provide statusinformation, and sequence numbers 605 and 630 assign a number to eachrecord for indicating whether the entire record set has been read fromthe host application. Write I/O type 606 is an indicator of the type ofwrite operation performed on each record. Search argument 607 indicatesinitial positioning information for the first read record set datarecord 620. A sector number 608 identifies the sector that the recordwas updated at, and count field 609 describes a number of specificrecord data fields 620 that follow. A host application time when thewrite update occurred is recorded in time of updates 610. Specificrecord data 620 provides a count/key/data (CKD) field of each recordupdate.

The collected information is journaled by a journal management systemwhich may comprise part of the storage data mover 29 or of the workloadmanager, or which may be implemented as a separate application 30 of thehost system 12. The journal management system is configured to store therecord set information in a journal. In one embodiment, the journal isinitially stored in cache 21. The journal forms a basis for formingconsistency groups by the storage system 10 and operating the storagecontrol system 25 to store the data of the consistency groups at storagedrives 26. To this end, the journal may be transferred to the cache 41of the secondary storage control system 25. The journal may be employedfor continuous data protection operations during data shadowingoperations. The journal continues to grow, for example for a shift or adays worth of data, and the journal management system maintains theinformation by offloading the journal to storage such as tape 17,employing the data storage system, and the journal provides theinformation to cover the specific time period of the shift or day. Thedata management system may alternatively or additionally offload thejournal to storage such as tape 47. Thus, an existing journal entry isjournaled together with all the information for all write I/O's thatmake up a specific point in time consistency group. That is, theinformation is for all write I/O's across all volumes on all storagesubsystems defined in the particular logical session, and the journal isa collection of consistency groups based on time.

Referring to FIG. 4, an alternative embodiment of a data storage system400 is illustrated in which a primary host 401 provides thecommunications with respect to the secondary site through a secondarybase 411. Two applications 402, 403 are illustrated and represent apotentially large number of applications. Data storage is run via a datamover 404 at the primary site 421, with a sysplex clock 407 of theprimary host, and via a data mover 414 at a secondary site 431. This isan arrangement discussed by the incorporated '818 patent, wherein thehost comprises at least one primary processor and at least one secondaryprocessor. An example of a processor is the IBM® ES/9000 having datamover software. Also at each site are storage controllers 405 and 415and direct access storage devices such as hard disk drives. Examples ofstorage controllers comprise IBM® 3990 storage controllers, and examplesof data storage drives comprise IBM® 3390 DASD.

In accordance with the present invention, the workload manager 300 maybe resident at the data mover 404. The workload manager 300 isconfigured to provide the service workload identification 100 of FIG. 2for use by an I/O subsystem 310 to be provided to the storage subsystemstorage controllers 405 via a Channel Command Word (CCW) or equivalent,such as the define extent CCW or the prefix CCW discussed above. Thestorage subsystem controllers 405 build Read Record Set prefix headers500 for the XRC volumes. The record set information 600 of FIG. 3 iscollected by the storage control system at data mover 404 and the datamover forms the consistency groups. The record set informationincorporates the service workload identification 100 from the ReadRecord Set prefix header 500. The journal management system may beresident in or with the workload manager 300, and the collectedinformation is journaled by the journal management system. In oneembodiment, the journal is initially stored in cache 301. The journalcomprises a basis for forming the consistency groups by the storagesystem at site 121 and the secondary data mover 414 is operated to storethe data of the consistency groups at secondary DASD 416. To this end,the journal may be transferred to the control info DASD 417 of thesecondary site 431. The journal may be employed for continuous dataprotection operations during data shadowing operations. The journalcontinues to grow, for example for a shift or a days worth of data, andthe journal management system, via the data mover 404 or other elementof the data storage system, offloads the journal to tape 317, and thejournal provides the information to cover the specific time period ofthe shift or day, as discussed above.

Referring to FIG. 5, functions implementing the present invention aredepicted, and in step 700, the customer, via the host 12, 401 of FIGS. 1and 4, has assigned a class of service or an I/O priority to each of theapplications 30, or alternatively, to different I/O operations for theapplications. A class of service designation may include or comprise anI/O priority, as discussed above. The class of service may reflectcustomer defined relative business priorities on a workload by workloadbasis. As discussed above, a class of service or I/O priority, or anysimilar designation is called “service workload identification”.

Still referring to FIG. 5, beginning in step 710, the data storagesystem 10, 400 of FIGS. 1 and 4, is configured to provide the serviceworkload identification describing the write I/O and to journal recordset information with the service workload identification. In step 720,the workload manager 20, 300 accesses its control blocks to establishthe class of service or the I/O priority for the current write I/O, andpulls the I/O priority for the governing class associated with this I/Ooperation. The service workload identification may comprise a class ofservice defined for the owning application by the host, wherein theclass of service may define the I/O priority information. The workloadmanager is configured to select the I/O priority information or theclass of service, and thereby identify the application to which the I/Obelongs.

In step 730, the workload manager 20, 300 provides the service workloadidentification for adding the service workload identification to thedefine extent CCW or prefix CCW or equivalent, and the data storagesystem generates the CCW. The CCW's are discussed above. The CCWprovides the service workload identification to the storage subsystemfor each XRC I/O.

In step 740, the storage subsystem sees that the I/O is directed to anXRC volume and builds the Read Record Set prefix with the storageinformation in its cache, and includes the service workloadidentification 100 of FIG. 2 in the Read Record Set prefix header 500.

In step 750 of FIG. 5, the data storage system collects the Read RecordSets for consistency groups and the journal management system stores therecord set information 600 in a journal, for example, in cache 21, 301of FIGS. 1 and 4. The journal continues to grow, for example for a shiftor a days worth of data, and the journal management system, via the datamover 404 or other part of the data storage system, maintains theinformation by offloading the journal to storage such as tape 17, 47,317, in step 760, and the journal provides the information to cover thespecific time period of the shift or day, as discussed above. Herein,the creation of the journal entries is deemed conducted by the journalmanagement system without regard for the specific application orapplications performing the specific collection and arrangement of theinformation, nor the formation and storage of the information as journalentries.

Thus, the journal entries are journaled together by consistency groupand form the information for all write I/O's for the time period of theshift or day, and each has the service workload identification, whichidentifies the application that originated the I/O. The journaledinformation may be employed for performing forensic analysis of datacorruption events or to perform security audits, etc., for example, byan operator at an operator panel 22 at the primary site, or at anoperator panel 770 at the secondary site, or through the host system 12of FIG. 1 or systems 401 or 411 of FIG. 4.

The service workload identification identifies the owning applicationthat provided the I/O, and allows a determination of which applicationupdated what data when. The journal entries also show, via theconsistency group, all other write I/Os to that or related volumes atthat specific time as well as times previous to the specific time inquestion. This information can be used to determine which applicationdid a write I/O that corrupted what data and at what specific time.Further, using this information with previous journal entries can allowdetermination of a write sequence by one application or others that mayhave led to the data corruption. In addition, subsequent journal entriesmay also indicate other data corruptions that may have occurred as theresult of the first corruption event. The tape may also be archived forfuture analysis if needed. In one example, a continuous data protectionapplication may provide the application interface to the journal, eitherin cache or from tape.

Those of skill in the art will understand that changes may be made withrespect to the methods discussed above, including changes to theordering of the steps. Further, those of skill in the art willunderstand that differing specific component arrangements may beemployed than those illustrated herein.

While the preferred embodiments of the present invention have beenillustrated in detail, it should be apparent that modifications andadaptations to those embodiments may occur to one skilled in the artwithout departing from the scope of the present invention as set forthin the following claims.

1. A data storage system configured to write data supplied from a hostto data storage in accordance with write I/O operations of owningapplications, comprising: a workload manager configured to direct theprocessing of supplied data in accordance with a write I/O of one ofsaid owning applications, configured to provide service workloadidentification for describing said write I/O, said service workloadidentification comprising at least a class of service defined for saidowning application by said host; at least one storage subsystemconfigured to add said service workload identification to record setinformation for said data, and a journal management system configured tostore information from said record set information in a journal,including said service workload identification.
 2. The data storagesystem of claim 1, wherein said at least one storage subsystem isconfigured to add said service workload identification into a ReadRecord Set prefix, and said journal management system is configured toprovide said information from said Read Record Set prefix to saidjournal.
 3. The data storage system of claim 2, wherein said workloadmanager is configured to provide said service workload identificationfor a defined extent Channel Command Word (CCW) which provides saidservice workload identification to said at least one storage subsystemfor said Read Record Set prefix.
 4. The data storage system of claim 2,wherein said workload manager is configured to provide said serviceworkload identification for a prefix Channel Command Word (CCW) whichprovides said service workload identification to said at least onestorage subsystem for said Read Record Set prefix.
 5. The data storagesystem of claim 1, wherein said class of service comprises I/O priorityinformation, and wherein said workload manager is configured to selectsaid I/O priority information of said class of service.
 6. A datastorage system, comprising: a plurality of data storage devices; and atleast one storage control system configured to store data supplied froma host to at least one of said data storage devices in accordance withwrite I/O operations of a plurality of owning applications, comprising:a workload manager configured to direct the processing of supplied datain accordance with a write I/O of one of said owning applications,configured to provide service workload identification for describingsaid write I/O, said service workload identification comprising at leasta class of service defined for said owning application by said host; atleast one storage subsystem control configured to add said serviceworkload identification to record set information for said data, and ajournal management system configured to store information from saidrecord set information in a journal, including said service workloadidentification.
 7. The data storage system of claim 6, wherein said atleast one storage subsystem control is configured to add said serviceworkload identification into a Read Record Set prefix, and said journalmanagement system is configured to provide said information from saidRead Record Set prefix to said journal.
 8. The data storage system ofclaim 7, wherein said workload manager is configured to provide saidservice workload identification for a defined extent Channel CommandWord (CCW) which provides said service workload identification to saidat least one storage subsystem control for said Read Record Set prefix.9. The data storage system of claim 7, wherein said workload manager isconfigured to provide said service workload identification for a prefixChannel Command Word (CCW) which provides said service workloadidentification to said at least one storage subsystem control for saidRead Record Set prefix.
 10. The data storage system of claim 6, whereinsaid class of service comprises I/O priority information, and whereinsaid workload manager is configured to select said I/O priorityinformation of said class of service.
 11. A data storage systemconfigured to write data supplied from a host to primary and secondarydata storage in accordance with write I/O operations of owningapplications, comprising: a secondary storage system configured to storesupplied data to said secondary data storage; and a primary storagesystem configured to store data supplied from a host to said primarydata storage in accordance with write I/O of one of said owningapplications, and to supply said data for said secondary data storagesystem, said primary storage system additionally comprising: a workloadmanager configured to direct the processing of said supplied data inaccordance with a write I/O of one of said owning applications,configured to provide service workload identification for describingsaid write I/O, said service workload identification comprising at leasta class of service defined for said owning application by said host; atleast one storage subsystem control configured to add said serviceworkload identification to record set information for said data, and ajournal management system configured to store information from saidrecord set information in a journal, including said service workloadidentification.
 12. The data storage system of claim 11, wherein saidprimary storage system at least one storage subsystem control isconfigured to add said service workload identification into a ReadRecord Set prefix, and said journal management system is configured toprovide said information from said Read Record Set prefix to saidjournal.
 13. The data storage system of claim 12, wherein said primarystorage system workload manager is configured to provide said serviceworkload identification for a defined extent Channel Command Word (CCW)which provides said service workload identification to said at least onestorage subsystem control for said Read Record Set prefix.
 14. The datastorage system of claim 12, wherein said primary storage system workloadmanager is configured to provide said service workload identificationfor a prefix Channel Command Word (CCW) which provides said serviceworkload identification to said at least one storage subsystem controlfor said Read Record Set prefix.
 15. The data storage system of claim11, wherein said class of service comprises I/O priority information,and wherein said primary storage system workload manager is configuredto select said I/O priority information of said class of service.